home *** CD-ROM | disk | FTP | other *** search
- Path: newsroom.utas.edu.au!usenet
- From: nring@dslip17.its.utas.edu.au (Nick Ring)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: ARexx Questions
- Date: 25 Feb 1996 20:15:37 GMT
- Organization: Private
- Distribution: world
- Message-ID: <4gqg19$2mv@franklin.its.utas.edu.au>
- References: <4gkpac$65c@epervier.CC.UMontreal.CA>
- NNTP-Posting-Host: dslip17.its.utas.edu.au
- Mime-Version: 1.0
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- X-NewsSoftware: GRn 2.1 Feb 19, 1994
-
- In article <4gkpac$65c@epervier.CC.UMontreal.CA> girardm@ERE.UMontreal.CA (Girard Michel) writes:
- >>Girard Michel (girardm@ERE.UMontreal.CA) wrote:
- >>>: Second:
- >>>: When the ARexx script is launch by Opus5, how can you know from where(path)
- >>>: the script come from.
-
- >>crnt_dir = pragma('D')
-
- >No when you do that you've got the path from where Opus5 start, in my case
- > sys:WBStartup.
- >And the only options opus offer is -CD Source or -CD Dest.!!!???
-
- Sorry, I forgot about that, as I haven't use DOpus for ages. You could
- when calling the ARexx script, have a CLI option where the current
- selected directory is passed to the script, ie.
-
- some_script.rexx CD=%sd
-
- where '%sd' is DOpus' meta-characters for source directory. I know it's
- not excatly what you want, but it is a fix.
-
- You could always query DOpus through it's ARexx port to see which is the
- current selected directory. This has the disadvantage of that your script
- has to do it first off if it is to run in the background.
-
- nick
-
-